Student Login

Search our website here...

Batch Job States

LL Batch Job states

When user issues llq commands, one of the columns reported is a job status. This is the table explaining what each of the job status codes mean.

Job state	Functional state	Abbreviation in displays / output	Description
Canceled	Terminating	CA	The job was canceled either by a user or by an administrator.
Complete Pending	Terminating	CP	The job is in the process of being completed.
Deferred	Idle	D	The job will not be assigned to a machine until a specified date. This date may have been specified by the user in the job command file, or may have been generated by the negotiator because a parallel job did not accumulate enough machines to run the job. Only the central manager places a job in the Deferred state.
Idle	Idle	I	The job is being considered to run on a machine, though no machine has been selected.
Not Queued	Idle	NQ	The job is not being considered to run on a machine. A job can enter this state because the associated Schedd is down, the user or group associated with the job is at its maximum maxqueued or maxidle value, or because the job has a dependency which cannot be determined. For more information on these keywords, see Controlling the mix of idle and running jobs. (Only the central manager places a job in the NotQueued state.)
Not Run	n/a	NR	The job will never be run because a dependency associated with the job was found to be false.
Pending	Running	P	The job is in the process of starting on one or more machines. (The negotiator indicates this state until the Schedd acknowledges that it has received the request to start the job. Then the negotiator changes the state of the job to Starting. The Schedd indicates the Pending state until all startd machines have acknowledged receipt of the start request. The Schedd then changes the state of the job to Starting.)
Preempted	Running	E	The job is preempted. This state applies only when LoadLeveler uses the suspend method to preempt the job.
Preempt Pending	Running	EP	The job is in the process of being preempted. This state applies only when LoadLeveler uses the suspend method to preempt the job.
Rejected	Idle	X	The job is rejected.
Reject Pending	Idle	XP	The job did not start. Possible reasons why a job is rejected are: job requirements were not met on the target machine, or the user ID of the person running the job is not valid on the target machine. After a job leaves the Reject Pending state, it is moved into one of the following states: Idle, User Hold, or Removed.
Removed	Terminating	RM	The job was stopped by LoadLeveler.
Remove Pending	Terminating	RP	The job is in the process of being removed, but not all associated machines have acknowledged the removal of the job.
Resume Pending	Running	MP	The job is in the process of being resumed.
Running	Running	R	The job is running: the job was dispatched and has started on the designated machine.
Starting	Running	ST	The job is starting: the job was dispatched, was received by the target machine, and LoadLeveler is setting up the environment in which to run the job. For a parallel job, LoadLeveler sets up the environment on all required nodes. See the description of the ¿Pending¿ state for more information on when the negotiator or the Schedd daemon moves a job into the Starting state.
System Hold	Idle	S	The job has been put in system hold.
Terminated	Terminating	TX	If the negotiator and Schedd daemons experience communication problems, they may be temporarily unable to exchange information concerning the status of jobs in the system. During this period of time, some of the jobs may actually complete and therefore be removed from the Schedd's list of active jobs. When communication resumes between the two daemons, the negotiator will move such jobs to the Terminated state, where they will remain for a set period of time (specified by the NEGOTIATOR_REMOVE_COMPLETED keyword in the configuration file). When this time has passed, the negotiator will remove the jobs from its active list.
User & System Hold	Idle	HS	The job has been put in both system hold and user hold.
User Hold	Idle	H	The job has been put in user hold.
Vacated	Idle	V	The job started but did not complete. The negotiator will reschedule the job (provided the job is allowed to be rescheduled). Possible reasons why a job moves to the Vacated state are: the machine where the job was running was flushed, the VACATE expression in the configuration file evaluated to True, or LoadLeveler detected a condition indicating the job needed to be vacated. For more information on the VACATE expression, see Managing job status through control expressions.
Vacate Pending	Idle	VP	The job is in the process of being vacated.